Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2271d965a9518cc8fae4eca1b83938fc0d945227484f8431bfd4054aafe47209

Tx prefix hash: d730abb6f1b01c90464f36ab669364e1e99fdfafc57eed1a191d6f3925dccd4a
Tx public key: ee181d4870a1aef7e9c0b47f28ce965b25fd3a8003db5374a2441849f9dc015b
Timestamp: 1747206367 Timestamp [UCT]: 2025-05-14 07:06:07 Age [y:d:h:m:s]: 00:263:02:59:44
Block: 1282581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185674 RingCT/type: yes/0
Extra: 01ee181d4870a1aef7e9c0b47f28ce965b25fd3a8003db5374a2441849f9dc015b02110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f810b7bd71bd4383df866b2c3278af4e0a2a4509d1f277087deb394e755fba2 0.600000000000 1769988 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": 1282591, "vin": [ { "gen": { "height": 1282581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f810b7bd71bd4383df866b2c3278af4e0a2a4509d1f277087deb394e755fba2" } } ], "extra": [ 1, 238, 24, 29, 72, 112, 161, 174, 247, 233, 192, 180, 127, 40, 206, 150, 91, 37, 253, 58, 128, 3, 219, 83, 116, 162, 68, 24, 73, 249, 220, 1, 91, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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