Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 032ee331a019fdbaa13df4100cc314c6c9af087b2dd6e80e9c6600e52385838e

Tx prefix hash: 8bf5e3161ac6e734a00016b39eeeeb2b5d374f8492c1d71f7672449b8d2da7c5
Tx public key: 7676ba7013b4926a2dcf04ad226033e62c25ab611c4e6bfa5eb17a17a7f19ba4
Timestamp: 1722737400 Timestamp [UCT]: 2024-08-04 02:10:00 Age [y:d:h:m:s]: 00:285:02:50:42
Block: 1080257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203677 RingCT/type: yes/0
Extra: 017676ba7013b4926a2dcf04ad226033e62c25ab611c4e6bfa5eb17a17a7f19ba402110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34b53c5148fc1cb8b8783e2fad6225aeea6684148796609f728b9dbd582dffff 0.600000000000 1553542 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": 1080267, "vin": [ { "gen": { "height": 1080257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34b53c5148fc1cb8b8783e2fad6225aeea6684148796609f728b9dbd582dffff" } } ], "extra": [ 1, 118, 118, 186, 112, 19, 180, 146, 106, 45, 207, 4, 173, 34, 96, 51, 230, 44, 37, 171, 97, 28, 78, 107, 250, 94, 177, 122, 23, 167, 241, 155, 164, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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