Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264ee90a1ff382c32443ff84c6fdddd6aea7b35c12eefc1f9b43e197447aba92

Tx prefix hash: c4c5957fbe01574e820d7dcf24e45e58ce69b23c2fe6d94237ddc6e4fe10d86d
Tx public key: e9b4c8cb8bbaf23b0494b286cf2524ec02be0634e42386137606f86738b9b65d
Timestamp: 1745064375 Timestamp [UCT]: 2025-04-19 12:06:15 Age [y:d:h:m:s]: 00:211:11:52:20
Block: 1264837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148881 RingCT/type: yes/0
Extra: 01e9b4c8cb8bbaf23b0494b286cf2524ec02be0634e42386137606f86738b9b65d021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df851d45d5d8dd4bbb2220d903e3d4e5f10c177a1676694550ac4c3e163b8701 0.600000000000 1752038 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": 1264847, "vin": [ { "gen": { "height": 1264837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df851d45d5d8dd4bbb2220d903e3d4e5f10c177a1676694550ac4c3e163b8701" } } ], "extra": [ 1, 233, 180, 200, 203, 139, 186, 242, 59, 4, 148, 178, 134, 207, 37, 36, 236, 2, 190, 6, 52, 228, 35, 134, 19, 118, 6, 248, 103, 56, 185, 182, 93, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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