Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f509ad74f7d82f681c5862b29e3ba090b37130ed3d1d9d2696742966dfee89

Tx prefix hash: 80de90a8db7885434c668a3c8f611c861511c3f863c1cf5b824b02bc64630b38
Tx public key: 63613194d731e9eeea36ced5a2635c8139c6519b0cdb1e32216c4647d2e92b34
Timestamp: 1728613425 Timestamp [UCT]: 2024-10-11 02:23:45 Age [y:d:h:m:s]: 00:230:12:58:19
Block: 1128965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164596 RingCT/type: yes/0
Extra: 0163613194d731e9eeea36ced5a2635c8139c6519b0cdb1e32216c4647d2e92b34021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5226531b374c934b607fa87b4942f27b66de3c07306d033b9b3a5c9228cf7dfe 0.600000000000 1611788 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": 1128975, "vin": [ { "gen": { "height": 1128965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5226531b374c934b607fa87b4942f27b66de3c07306d033b9b3a5c9228cf7dfe" } } ], "extra": [ 1, 99, 97, 49, 148, 215, 49, 233, 238, 234, 54, 206, 213, 162, 99, 92, 129, 57, 198, 81, 155, 12, 219, 30, 50, 33, 108, 70, 71, 210, 233, 43, 52, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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