Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d36bbd48a034ba2e331bf96df9863d5f68036bdc3d81910f1392b503bec27a93

Tx prefix hash: 31495a1b5944d248db1e955a7ba843be6ab6587aa403c257bbb814c7595882c4
Tx public key: 02322f03f78d59a35b36358077357e9bbd3a6f20c7bb1dabdcd1dbc8d3c87690
Timestamp: 1703070160 Timestamp [UCT]: 2023-12-20 11:02:40 Age [y:d:h:m:s]: 01:349:01:54:21
Block: 917202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508376 RingCT/type: yes/0
Extra: 0102322f03f78d59a35b36358077357e9bbd3a6f20c7bb1dabdcd1dbc8d3c8769002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 280e0c29fd44b2fb77d92df495ed11b0916d12b0eb2320bd5041a33c4007da15 0.600000000000 1374772 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": 917212, "vin": [ { "gen": { "height": 917202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "280e0c29fd44b2fb77d92df495ed11b0916d12b0eb2320bd5041a33c4007da15" } } ], "extra": [ 1, 2, 50, 47, 3, 247, 141, 89, 163, 91, 54, 53, 128, 119, 53, 126, 155, 189, 58, 111, 32, 199, 187, 29, 171, 220, 209, 219, 200, 211, 200, 118, 144, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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