Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ca7d1e6ab358df9ebb08e95fda26f04805f6d0ee7f9ee282a10916860bb1fd

Tx prefix hash: 23db628a820e30d19eed353e4d985ed77834bf20d16fe06ece8a5956179b324e
Tx public key: 07d8e0ce48ad88f448e099983e5b2a66450a1a39a8f5c286891f5fb12a5140d8
Timestamp: 1752631094 Timestamp [UCT]: 2025-07-16 01:58:14 Age [y:d:h:m:s]: 00:168:02:44:24
Block: 1326407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118957 RingCT/type: yes/0
Extra: 0107d8e0ce48ad88f448e099983e5b2a66450a1a39a8f5c286891f5fb12a5140d802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c6474dfdeb4f49ad1376df8e6326aca709e4c86b24d11258315599987d43f60 0.600000000000 1814158 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": 1326417, "vin": [ { "gen": { "height": 1326407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c6474dfdeb4f49ad1376df8e6326aca709e4c86b24d11258315599987d43f60" } } ], "extra": [ 1, 7, 216, 224, 206, 72, 173, 136, 244, 72, 224, 153, 152, 62, 91, 42, 102, 69, 10, 26, 57, 168, 245, 194, 134, 137, 31, 95, 177, 42, 81, 64, 216, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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