Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d4dd0816121fa26daf47b785a347ff44b90991cd9d0c3c15d3e38b4686a2c043

Tx prefix hash: cfc098ee3921cb665763d0a3ef34452c5ae1f81140d104eac31f11c1706e7edb
Tx public key: 5799a9b44c93b7f84215f7d1dadae94f576c5f0bf7665be1ecc3d587f552548f
Timestamp: 1760542878 Timestamp [UCT]: 2025-10-15 15:41:18 Age [y:d:h:m:s]: 00:082:07:12:47
Block: 1390560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58951 RingCT/type: yes/0
Extra: 015799a9b44c93b7f84215f7d1dadae94f576c5f0bf7665be1ecc3d587f552548f0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad5bb9cf11a9e64747d1e080a09788b4a188cac59519a1ef97d689c702c48ba 0.600000000000 1878807 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1390570, "vin": [ { "gen": { "height": 1390560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad5bb9cf11a9e64747d1e080a09788b4a188cac59519a1ef97d689c702c48ba" } } ], "extra": [ 1, 87, 153, 169, 180, 76, 147, 183, 248, 66, 21, 247, 209, 218, 218, 233, 79, 87, 108, 95, 11, 247, 102, 91, 225, 236, 195, 213, 135, 245, 82, 84, 143, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8