Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391b3aeb4e12b24076bcb24db9a9afb8e659e1046c5bb1b554eb37ad555d0301

Tx prefix hash: 4146cd91fb0a0549360e3107730ea7d8e6a0be04bb6c743e88f01ac8e7c286a9
Tx public key: 3d69910ee321e63598475c3e06dca2f4835b8ebbf12d0f8a358cca5bbd8dd3f6
Timestamp: 1701877275 Timestamp [UCT]: 2023-12-06 15:41:15 Age [y:d:h:m:s]: 01:186:15:09:35
Block: 907301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394595 RingCT/type: yes/0
Extra: 013d69910ee321e63598475c3e06dca2f4835b8ebbf12d0f8a358cca5bbd8dd3f602110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.604971786000 dcy

stealth address amount amount idx
00: 83519e4a68ffca6e89003632c40e1f210fbcc2f10e1c52918894c7d6dc5bbe87 0.604971786000 1364284 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": 907311, "vin": [ { "gen": { "height": 907301 } } ], "vout": [ { "amount": 604971786, "target": { "key": "83519e4a68ffca6e89003632c40e1f210fbcc2f10e1c52918894c7d6dc5bbe87" } } ], "extra": [ 1, 61, 105, 145, 14, 227, 33, 230, 53, 152, 71, 92, 62, 6, 220, 162, 244, 131, 91, 142, 187, 241, 45, 15, 138, 53, 140, 202, 91, 189, 141, 211, 246, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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