Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ec2c41f68350365c3bfa7c20c631f0e104012535d4b9ed468b45dc75b14743

Tx prefix hash: 5e3bb81fdb8159b78361b983314d5243dbcde9cf29b22ce7c8a8f2ebf347ff08
Tx public key: 28e0ff02316fd8cd7f236dc83a88019f11de7eb916782c4b8f99d91ca98ca346
Timestamp: 1583347865 Timestamp [UCT]: 2020-03-04 18:51:05 Age [y:d:h:m:s]: 05:219:02:04:21
Block: 76541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1309150 RingCT/type: yes/0
Extra: 0128e0ff02316fd8cd7f236dc83a88019f11de7eb916782c4b8f99d91ca98ca34602110000003a12c4732d000000000000000000

1 output(s) for total of 342.285647003000 dcy

stealth address amount amount idx
00: ca6e7bc67d8f38e3357fe6bdeeccbfa2c2d9a14f16d931f9009438ed2c9c0578 342.285647003000 140817 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": 76551, "vin": [ { "gen": { "height": 76541 } } ], "vout": [ { "amount": 342285647003, "target": { "key": "ca6e7bc67d8f38e3357fe6bdeeccbfa2c2d9a14f16d931f9009438ed2c9c0578" } } ], "extra": [ 1, 40, 224, 255, 2, 49, 111, 216, 205, 127, 35, 109, 200, 58, 136, 1, 159, 17, 222, 126, 185, 22, 120, 44, 75, 143, 153, 217, 28, 169, 140, 163, 70, 2, 17, 0, 0, 0, 58, 18, 196, 115, 45, 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