Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5132b454d3f195deb64740fc09636b95c909ab96beb5b3f8289f6ff8402e7aad

Tx prefix hash: f6e1ab9079e45dca671180449f6cda1241cb6e4d182ac48a6319315163ccc39f
Tx public key: e9be268921334f2e782170bd79e2a9c0f5dcb24e5838c8af616b7ff863e5cbf1
Timestamp: 1699713627 Timestamp [UCT]: 2023-11-11 14:40:27 Age [y:d:h:m:s]: 01:147:20:41:19
Block: 889371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366862 RingCT/type: yes/0
Extra: 01e9be268921334f2e782170bd79e2a9c0f5dcb24e5838c8af616b7ff863e5cbf102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.693656852000 dcy

stealth address amount amount idx
00: ac099954ba37ad343882134058bec0ffe54810e0eab731f9e5d59523fc3436f3 0.693656852000 1345366 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": 889381, "vin": [ { "gen": { "height": 889371 } } ], "vout": [ { "amount": 693656852, "target": { "key": "ac099954ba37ad343882134058bec0ffe54810e0eab731f9e5d59523fc3436f3" } } ], "extra": [ 1, 233, 190, 38, 137, 33, 51, 79, 46, 120, 33, 112, 189, 121, 226, 169, 192, 245, 220, 178, 78, 88, 56, 200, 175, 97, 107, 127, 248, 99, 229, 203, 241, 2, 17, 0, 0, 0, 1, 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