Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e0d1819b574aa5cdb1d34eb0f6ad447a5926deead07592747a9e28f8d77aa3

Tx prefix hash: 9db94e4ecec75f4c9a4b97c02d110e6aadcd8ae5a5a4ea82ba1566fc943477a4
Tx public key: 0b2a5a450975b76428089bec79f71b0669838c41ffeeb6d0980d89f7a39f3cec
Timestamp: 1731182155 Timestamp [UCT]: 2024-11-09 19:55:55 Age [y:d:h:m:s]: 00:186:02:55:11
Block: 1150179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132873 RingCT/type: yes/0
Extra: 010b2a5a450975b76428089bec79f71b0669838c41ffeeb6d0980d89f7a39f3cec021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9102874389bd5b64df68887b6a35895dd68f927563e762ee18f5bd5b66a2d866 0.600000000000 1635410 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": 1150189, "vin": [ { "gen": { "height": 1150179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9102874389bd5b64df68887b6a35895dd68f927563e762ee18f5bd5b66a2d866" } } ], "extra": [ 1, 11, 42, 90, 69, 9, 117, 183, 100, 40, 8, 155, 236, 121, 247, 27, 6, 105, 131, 140, 65, 255, 238, 182, 208, 152, 13, 137, 247, 163, 159, 60, 236, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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