Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5ca8eec57d911311bb25b97ab36ddae12a16e6a97f1b1f2a2318e854345298b

Tx prefix hash: 2087aef13e2883c429f57233b419c4f21099546719bc67a881fd7d7743f1a937
Tx public key: 6bf2f3587b069280c7e9ca9e0aea9960e09a304724962edf1db3c377a8697311
Timestamp: 1714055805 Timestamp [UCT]: 2024-04-25 14:36:45 Age [y:d:h:m:s]: 00:248:00:45:28
Block: 1008275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177526 RingCT/type: yes/0
Extra: 016bf2f3587b069280c7e9ca9e0aea9960e09a304724962edf1db3c377a86973110211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30b9388cc4376bdec1dbd646457fe4c33b2d449f8b803feb64b0f62a2ed6e71a 0.600000000000 1469743 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": 1008285, "vin": [ { "gen": { "height": 1008275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30b9388cc4376bdec1dbd646457fe4c33b2d449f8b803feb64b0f62a2ed6e71a" } } ], "extra": [ 1, 107, 242, 243, 88, 123, 6, 146, 128, 199, 233, 202, 158, 10, 234, 153, 96, 224, 154, 48, 71, 36, 150, 46, 223, 29, 179, 195, 119, 168, 105, 115, 17, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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