Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 270a6c0cf6eeb56842aa9b8fbbf73b224da0d8c2942fce2c4948770b85cd8805

Tx prefix hash: d7bdb4e8706171ea90f625c9efcd61b684ed2232659a248825b027c6ea860768
Tx public key: a0eac39ef57edbdf5cf816589e1ec0fdeb20e29c0f07200292ad8d12a1d7ff28
Timestamp: 1649545764 Timestamp [UCT]: 2022-04-09 23:09:24 Age [y:d:h:m:s]: 03:257:23:46:00
Block: 476867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 962589 RingCT/type: yes/0
Extra: 01a0eac39ef57edbdf5cf816589e1ec0fdeb20e29c0f07200292ad8d12a1d7ff28021100000001bf7ee4e7000000000000000000

1 output(s) for total of 16.141706448000 dcy

stealth address amount amount idx
00: 6a3bbf575f3f272cd30a223e230b51c1ad3218bca76248a7aa94c187289449a1 16.141706448000 897444 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": 476877, "vin": [ { "gen": { "height": 476867 } } ], "vout": [ { "amount": 16141706448, "target": { "key": "6a3bbf575f3f272cd30a223e230b51c1ad3218bca76248a7aa94c187289449a1" } } ], "extra": [ 1, 160, 234, 195, 158, 245, 126, 219, 223, 92, 248, 22, 88, 158, 30, 192, 253, 235, 32, 226, 156, 15, 7, 32, 2, 146, 173, 141, 18, 161, 215, 255, 40, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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