Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c29efaf48cc2ef1eb57d171268e416b307d68f64facbe30e03f91e645814377

Tx prefix hash: 12fa02b9439c778110f6a857cb092994e738d262df4201e0aaa109ca1764857f
Tx public key: 08f24f689056c1f23fb7cb264f7e8e3ec8c39daa09561834cdb9c3a48afed652
Timestamp: 1715359268 Timestamp [UCT]: 2024-05-10 16:41:08 Age [y:d:h:m:s]: 00:362:21:48:50
Block: 1019081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259423 RingCT/type: yes/0
Extra: 0108f24f689056c1f23fb7cb264f7e8e3ec8c39daa09561834cdb9c3a48afed65202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d7e79d1d274f387e2d3e7fb08155d4cdb11273b09f99c4d58ad28e14aaac894 0.600000000000 1482954 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": 1019091, "vin": [ { "gen": { "height": 1019081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7e79d1d274f387e2d3e7fb08155d4cdb11273b09f99c4d58ad28e14aaac894" } } ], "extra": [ 1, 8, 242, 79, 104, 144, 86, 193, 242, 63, 183, 203, 38, 79, 126, 142, 62, 200, 195, 157, 170, 9, 86, 24, 52, 205, 185, 195, 164, 138, 254, 214, 82, 2, 17, 0, 0, 0, 4, 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