Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9236de7d1cfeb6ff8fa6b4f033677d9522ef0349377848aa8890ae2c5138eb

Tx prefix hash: 4dabf5ac1e508b4e33a744700bbb52df9c330914c33defd58df8c65557b6c083
Tx public key: bf7b05512a9485e2e7298d2de8beb0a6932cf131d0b7f5471dcfae7e7fed5e49
Timestamp: 1699811040 Timestamp [UCT]: 2023-11-12 17:44:00 Age [y:d:h:m:s]: 01:137:12:05:18
Block: 890182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359453 RingCT/type: yes/0
Extra: 01bf7b05512a9485e2e7298d2de8beb0a6932cf131d0b7f5471dcfae7e7fed5e490211000000011053e0c1000000000000000000

1 output(s) for total of 0.689378127000 dcy

stealth address amount amount idx
00: c6d2e5b76f807872ad5b2096c3e75855614b8236d50a70351e8f331e2bce187a 0.689378127000 1346203 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": 890192, "vin": [ { "gen": { "height": 890182 } } ], "vout": [ { "amount": 689378127, "target": { "key": "c6d2e5b76f807872ad5b2096c3e75855614b8236d50a70351e8f331e2bce187a" } } ], "extra": [ 1, 191, 123, 5, 81, 42, 148, 133, 226, 231, 41, 141, 45, 232, 190, 176, 166, 147, 44, 241, 49, 208, 183, 245, 71, 29, 207, 174, 126, 127, 237, 94, 73, 2, 17, 0, 0, 0, 1, 16, 83, 224, 193, 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