Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d496ef613f3dc4b11a1f14f537fa7c98b9bbbb1c8d6172901397445496c39dda

Tx prefix hash: 58ef5f5d0a8107184dc0b13d5ed912d5b4a17dd9917ed71b1cc37dfe959830e0
Tx public key: b2cedaf39b4a83e126b42fb91ee1344030ec825d4cc14196348b263c9d2aa5a8
Timestamp: 1726209781 Timestamp [UCT]: 2024-09-13 06:43:01 Age [y:d:h:m:s]: 00:119:13:28:16
Block: 1109028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85512 RingCT/type: yes/0
Extra: 01b2cedaf39b4a83e126b42fb91ee1344030ec825d4cc14196348b263c9d2aa5a8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62038303b93bc65eba126ba4a2b09fbcd5ce09242a07b483e2774152218304e0 0.600000000000 1587137 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": 1109038, "vin": [ { "gen": { "height": 1109028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62038303b93bc65eba126ba4a2b09fbcd5ce09242a07b483e2774152218304e0" } } ], "extra": [ 1, 178, 206, 218, 243, 155, 74, 131, 225, 38, 180, 47, 185, 30, 225, 52, 64, 48, 236, 130, 93, 76, 193, 65, 150, 52, 139, 38, 60, 157, 42, 165, 168, 2, 17, 0, 0, 0, 1, 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