Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953955c6d202e6ca2ff7f4d7af9d5f3cde521a3ba1df25369c44552201926719

Tx prefix hash: 070a588f62e7e560ec832ab4d25969245545265f67628b388fbf6869371939b5
Tx public key: 3e86e89e7058e44d17c2e3dd674e9745c7d949af98c9df292e264af9ccb031ed
Timestamp: 1578091677 Timestamp [UCT]: 2020-01-03 22:47:57 Age [y:d:h:m:s]: 04:360:15:48:47
Block: 38049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147014 RingCT/type: yes/0
Extra: 013e86e89e7058e44d17c2e3dd674e9745c7d949af98c9df292e264af9ccb031ed0211000000054ac5aa02000000000000000000

1 output(s) for total of 459.122650169000 dcy

stealth address amount amount idx
00: fdba514195d33fff1d827e5b5d3eed79798651f592c874511999d0568684a7d5 459.122650169000 64706 of 0

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": 38059, "vin": [ { "gen": { "height": 38049 } } ], "vout": [ { "amount": 459122650169, "target": { "key": "fdba514195d33fff1d827e5b5d3eed79798651f592c874511999d0568684a7d5" } } ], "extra": [ 1, 62, 134, 232, 158, 112, 88, 228, 77, 23, 194, 227, 221, 103, 78, 151, 69, 199, 217, 73, 175, 152, 201, 223, 41, 46, 38, 74, 249, 204, 176, 49, 237, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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