Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d4aceeab4130fbaa6d6a041d6ee09f5ec12e90fa157fc11f758f86b49e28657

Tx prefix hash: 916a4d47f8990862ab5b10e0dadb2f8cb9bf67006e3bc3fd3ed950b4f5375ecd
Tx public key: b1560b0c6b66878c4665744ef0dd3be992ac7e95cbe6dc27ed36196e0191dcd8
Timestamp: 1714438512 Timestamp [UCT]: 2024-04-30 00:55:12 Age [y:d:h:m:s]: 00:216:06:53:18
Block: 1011441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154838 RingCT/type: yes/0
Extra: 01b1560b0c6b66878c4665744ef0dd3be992ac7e95cbe6dc27ed36196e0191dcd80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47fd8ac955ad814f2ad06045b801ecd5ee3d67581cf6f9899b7015a55e660eea 0.600000000000 1473675 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": 1011451, "vin": [ { "gen": { "height": 1011441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47fd8ac955ad814f2ad06045b801ecd5ee3d67581cf6f9899b7015a55e660eea" } } ], "extra": [ 1, 177, 86, 11, 12, 107, 102, 135, 140, 70, 101, 116, 78, 240, 221, 59, 233, 146, 172, 126, 149, 203, 230, 220, 39, 237, 54, 25, 110, 1, 145, 220, 216, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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