Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23124a3cdf3f0b23b8dbf9989700975e394a7fd9712466d8c286daeb82cd9238

Tx prefix hash: e6a9969148e939d83b1f08355c9f672d4d85661d2f068128daad57c886a42f1c
Tx public key: 4d42041c2d970d9516cda5dd21674908432ee10a1f4197c6d1ba960a3f4597b8
Timestamp: 1702987263 Timestamp [UCT]: 2023-12-19 12:01:03 Age [y:d:h:m:s]: 01:098:01:48:40
Block: 916513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331209 RingCT/type: yes/0
Extra: 014d42041c2d970d9516cda5dd21674908432ee10a1f4197c6d1ba960a3f4597b802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 016b55c0d3dcb1d105781222c129505e4c94351b98aa87afc80e7ad6a634246c 0.600000000000 1374065 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": 916523, "vin": [ { "gen": { "height": 916513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "016b55c0d3dcb1d105781222c129505e4c94351b98aa87afc80e7ad6a634246c" } } ], "extra": [ 1, 77, 66, 4, 28, 45, 151, 13, 149, 22, 205, 165, 221, 33, 103, 73, 8, 67, 46, 225, 10, 31, 65, 151, 198, 209, 186, 150, 10, 63, 69, 151, 184, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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