Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2774ce4cfb12de7ae5ba8ad5cf801a4b164b2976c21d5b0354763b98e814ddf

Tx prefix hash: 2429e36cb4263835fa804c485f0aadb922a8c5153623ff635884b4a8e7566e0d
Tx public key: 91ac903f4a13d317960b739b020fbbc37f9bb1dd301033d48b5c3de48b52dbfb
Timestamp: 1702589109 Timestamp [UCT]: 2023-12-14 21:25:09 Age [y:d:h:m:s]: 01:120:22:59:24
Block: 913198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347604 RingCT/type: yes/0
Extra: 0191ac903f4a13d317960b739b020fbbc37f9bb1dd301033d48b5c3de48b52dbfb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66699380db9e52b7050254952d9b5b481c7cb2825188a13bda47b4f42caeb27e 0.600000000000 1370444 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": 913208, "vin": [ { "gen": { "height": 913198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66699380db9e52b7050254952d9b5b481c7cb2825188a13bda47b4f42caeb27e" } } ], "extra": [ 1, 145, 172, 144, 63, 74, 19, 211, 23, 150, 11, 115, 155, 2, 15, 187, 195, 127, 155, 177, 221, 48, 16, 51, 212, 139, 92, 61, 228, 139, 82, 219, 251, 2, 17, 0, 0, 0, 4, 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