Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98467ff8f61cdacbea44cdaa29d533483d12268a4cbca7585e00b2b5e3c1e303

Tx prefix hash: af076c63ab82653ccb359e3712d7fc63da7a6a0ff6983d664feca6321980674a
Tx public key: 4657c818f3884d041dc56882b535f2c74b2bbecb93b4f838cf8ac9ae36b105c0
Timestamp: 1649482684 Timestamp [UCT]: 2022-04-09 05:38:04 Age [y:d:h:m:s]: 03:037:17:10:26
Block: 476347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 807400 RingCT/type: yes/0
Extra: 014657c818f3884d041dc56882b535f2c74b2bbecb93b4f838cf8ac9ae36b105c002110000000406faf294000000000000000000

1 output(s) for total of 16.205591531000 dcy

stealth address amount amount idx
00: d0660234c49d42cb85187333ecdf2bad45a1ec8fe732c1193eaa6752834f8fae 16.205591531000 896788 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": 476357, "vin": [ { "gen": { "height": 476347 } } ], "vout": [ { "amount": 16205591531, "target": { "key": "d0660234c49d42cb85187333ecdf2bad45a1ec8fe732c1193eaa6752834f8fae" } } ], "extra": [ 1, 70, 87, 200, 24, 243, 136, 77, 4, 29, 197, 104, 130, 181, 53, 242, 199, 75, 43, 190, 203, 147, 180, 248, 56, 207, 138, 201, 174, 54, 177, 5, 192, 2, 17, 0, 0, 0, 4, 6, 250, 242, 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