Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59cd1f2a39117edf2324b2356f6f5832da0158383c1be05f1cc9623b13c1dc4d

Tx prefix hash: 55065e8b172fc21f2b77d2126230e0521c3cba62d8c993f274498477446d10c4
Tx public key: acf012384d6f506e4ec1a138414269e1fdb2e90305ce5a9e2d7065adeead39e5
Timestamp: 1720138213 Timestamp [UCT]: 2024-07-05 00:10:13 Age [y:d:h:m:s]: 00:323:13:13:48
Block: 1058697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231225 RingCT/type: yes/0
Extra: 01acf012384d6f506e4ec1a138414269e1fdb2e90305ce5a9e2d7065adeead39e502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72fe554f5a8f3f5032f85adefd6aa80a43e49d68f04c5119888bb6a311328e62 0.600000000000 1529154 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": 1058707, "vin": [ { "gen": { "height": 1058697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72fe554f5a8f3f5032f85adefd6aa80a43e49d68f04c5119888bb6a311328e62" } } ], "extra": [ 1, 172, 240, 18, 56, 77, 111, 80, 110, 78, 193, 161, 56, 65, 66, 105, 225, 253, 178, 233, 3, 5, 206, 90, 158, 45, 112, 101, 173, 238, 173, 57, 229, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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