Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0016581accb157dfd4aa61ae17b1909c69adac65e1e395f8c1f93c3ba71eb806

Tx prefix hash: b9aa2b0fcb724a3b0a17b23a3c421f042b60032640957cff77bff302e25f8152
Tx public key: e7aa5c571ed2f87725d4cd0a6cd08bf0f23f6ffa5b931cac94ddf8d720b8d2e0
Timestamp: 1702314282 Timestamp [UCT]: 2023-12-11 17:04:42 Age [y:d:h:m:s]: 01:119:21:49:33
Block: 910935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346836 RingCT/type: yes/0
Extra: 01e7aa5c571ed2f87725d4cd0a6cd08bf0f23f6ffa5b931cac94ddf8d720b8d2e002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23326a4eba6697e7cfa90d71b49ef9a173d58c730af8d01433bbbc6b180545cf 0.600000000000 1368110 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": 910945, "vin": [ { "gen": { "height": 910935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23326a4eba6697e7cfa90d71b49ef9a173d58c730af8d01433bbbc6b180545cf" } } ], "extra": [ 1, 231, 170, 92, 87, 30, 210, 248, 119, 37, 212, 205, 10, 108, 208, 139, 240, 242, 63, 111, 250, 91, 147, 28, 172, 148, 221, 248, 215, 32, 184, 210, 224, 2, 17, 0, 0, 0, 2, 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