Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c4cf1873ce4931369527191a7094a7bc2f7feb9f4b28977ea771c5d1ac2578f

Tx prefix hash: 4ec216484372cc461acdae1f65bb32e9d2c757439dff723f44c937d64b3e2ad8
Tx public key: 9ff67935dc912465501de8b1b51fb0893c19db2a717a18b9115f88d47a63fab8
Timestamp: 1722901152 Timestamp [UCT]: 2024-08-05 23:39:12 Age [y:d:h:m:s]: 00:110:15:58:49
Block: 1081611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79179 RingCT/type: yes/0
Extra: 019ff67935dc912465501de8b1b51fb0893c19db2a717a18b9115f88d47a63fab8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3401699c62e2a5ca5a010017829869dbf80ad8c263febae1a2e29182732cc2e 0.600000000000 1555424 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": 1081621, "vin": [ { "gen": { "height": 1081611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3401699c62e2a5ca5a010017829869dbf80ad8c263febae1a2e29182732cc2e" } } ], "extra": [ 1, 159, 246, 121, 53, 220, 145, 36, 101, 80, 29, 232, 177, 181, 31, 176, 137, 60, 25, 219, 42, 113, 122, 24, 185, 17, 95, 136, 212, 122, 99, 250, 184, 2, 17, 0, 0, 0, 2, 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