Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ee9be52ccc6f5e087294f45f2bb380741ca92fa3a9386913c1bb3ad8d25128

Tx prefix hash: 1bae5d5c3e7e7e5fcb688e15d34e449272059d4412558c557c0df591cc432cea
Tx public key: d0c4112741e91eaa68df643a698788f56a71d17a3e3f24e409e7eba41468487b
Timestamp: 1717236195 Timestamp [UCT]: 2024-06-01 10:03:15 Age [y:d:h:m:s]: 01:162:14:16:26
Block: 1034651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374784 RingCT/type: yes/0
Extra: 01d0c4112741e91eaa68df643a698788f56a71d17a3e3f24e409e7eba41468487b02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58657f233196f3d3d3ca7045c81bf9005eb453db46e8584123b71a9f2fcca95d 0.600000000000 1503166 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": 1034661, "vin": [ { "gen": { "height": 1034651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58657f233196f3d3d3ca7045c81bf9005eb453db46e8584123b71a9f2fcca95d" } } ], "extra": [ 1, 208, 196, 17, 39, 65, 233, 30, 170, 104, 223, 100, 58, 105, 135, 136, 245, 106, 113, 209, 122, 62, 63, 36, 228, 9, 231, 235, 164, 20, 104, 72, 123, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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