Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71e4a7d4d5c363fe56d216d37ae7e515dedebed77624ba8351610f09a2ba8111

Tx prefix hash: 1ed2c84d1c712fae5989c7ff76f672ba9068aa385a6406e1f25de72cd622d900
Tx public key: 1e4a1c912a3ba52cdb4607b216e581777ec5f45fdfd7ebaa53f00b17093e5092
Timestamp: 1720133296 Timestamp [UCT]: 2024-07-04 22:48:16 Age [y:d:h:m:s]: 00:324:01:15:25
Block: 1058654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231592 RingCT/type: yes/0
Extra: 011e4a1c912a3ba52cdb4607b216e581777ec5f45fdfd7ebaa53f00b17093e50920211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4cbfa863bb800d36b916dad9017311ef84fd3d41263818ce1083a526fff26bb 0.600000000000 1529111 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": 1058664, "vin": [ { "gen": { "height": 1058654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4cbfa863bb800d36b916dad9017311ef84fd3d41263818ce1083a526fff26bb" } } ], "extra": [ 1, 30, 74, 28, 145, 42, 59, 165, 44, 219, 70, 7, 178, 22, 229, 129, 119, 126, 197, 244, 95, 223, 215, 235, 170, 83, 240, 11, 23, 9, 62, 80, 146, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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