Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398d445681516b8e60e2fb733e149f30b6fc8864633c132ca183a5d43c83de68

Tx prefix hash: de0a3ae87ee757babc6618c7ea2d12b315e8bce0b7543e6638050322598fdee4
Tx public key: ce1c4e9463e560e12cf1b2442aacaadd36d5f3159b99657f21d80b1fbf7cba38
Timestamp: 1710006972 Timestamp [UCT]: 2024-03-09 17:56:12 Age [y:d:h:m:s]: 00:235:19:33:54
Block: 974716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168836 RingCT/type: yes/0
Extra: 01ce1c4e9463e560e12cf1b2442aacaadd36d5f3159b99657f21d80b1fbf7cba380211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db54d851ed3dc0367d22a654345260f1cf69b5ff55d43aa60a6c5bc15a06512 0.600000000000 1434675 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": 974726, "vin": [ { "gen": { "height": 974716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db54d851ed3dc0367d22a654345260f1cf69b5ff55d43aa60a6c5bc15a06512" } } ], "extra": [ 1, 206, 28, 78, 148, 99, 229, 96, 225, 44, 241, 178, 68, 42, 172, 170, 221, 54, 213, 243, 21, 155, 153, 101, 127, 33, 216, 11, 31, 191, 124, 186, 56, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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