Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5054c5b8a3a7e942b4b4303efbf6a3951459d2021eafb50a3ecdd8a7e9ca2d14

Tx prefix hash: 2f756cf3403bae6339bd9436e341647726a7ed16518d11556ea6c9fc8bda95a5
Tx public key: 1bb16d95b0897428c77fb1536ec756c5ca006b81ee1e1d6e4ba11e79b7ed532b
Timestamp: 1764217335 Timestamp [UCT]: 2025-11-27 04:22:15 Age [y:d:h:m:s]: 00:026:23:17:47
Block: 1421009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19302 RingCT/type: yes/0
Extra: 011bb16d95b0897428c77fb1536ec756c5ca006b81ee1e1d6e4ba11e79b7ed532b0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ee44d66c863338895ae2d8d24fbfc322986053114eea43f1e0c4a42cb69b0a 0.600000000000 1909564 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": 1421019, "vin": [ { "gen": { "height": 1421009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ee44d66c863338895ae2d8d24fbfc322986053114eea43f1e0c4a42cb69b0a" } } ], "extra": [ 1, 27, 177, 109, 149, 176, 137, 116, 40, 199, 127, 177, 83, 110, 199, 86, 197, 202, 0, 107, 129, 238, 30, 29, 110, 75, 161, 30, 121, 183, 237, 83, 43, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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