Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97c1047252cba303fe99be0227df9cfb4ae8e96b5419644ac98fcada325905d2

Tx prefix hash: c43736b43816832d0237250dc7c6c694192d973e6725a0ee031cc852bce1d3a2
Tx public key: 40f346b641cd43c0644807c3e5bfd4ddfb3493e72063b910f4ddafe6ea08be4e
Timestamp: 1682289213 Timestamp [UCT]: 2023-04-23 22:33:33 Age [y:d:h:m:s]: 01:360:19:30:16
Block: 745163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519146 RingCT/type: yes/0
Extra: 0140f346b641cd43c0644807c3e5bfd4ddfb3493e72063b910f4ddafe6ea08be4e021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.084327024000 dcy

stealth address amount amount idx
00: e8ad2b4d2daaeeca3e5748c4a4d09d67ead9f079242d38977748e464ece3b865 2.084327024000 1192588 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": 745173, "vin": [ { "gen": { "height": 745163 } } ], "vout": [ { "amount": 2084327024, "target": { "key": "e8ad2b4d2daaeeca3e5748c4a4d09d67ead9f079242d38977748e464ece3b865" } } ], "extra": [ 1, 64, 243, 70, 182, 65, 205, 67, 192, 100, 72, 7, 195, 229, 191, 212, 221, 251, 52, 147, 231, 32, 99, 185, 16, 244, 221, 175, 230, 234, 8, 190, 78, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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