Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a14115ec193bf3b02d5c5cc607611485b98c0cba5fb26804930f9ba7ff04bb4b

Tx prefix hash: a1f71195ad2f781698053441fc663792cfbd4d4bb2a9ad8b21ccce497b2f32d5
Tx public key: ab50a55e25e71d96dfd548b1a1ef741d093d08d9c6b561261cbcc567a19f1b28
Timestamp: 1746358594 Timestamp [UCT]: 2025-05-04 11:36:34 Age [y:d:h:m:s]: 00:233:06:21:10
Block: 1275551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164476 RingCT/type: yes/0
Extra: 01ab50a55e25e71d96dfd548b1a1ef741d093d08d9c6b561261cbcc567a19f1b28021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 796c2299578bea48aedb22ceab4a4067bc6aa4a622eb90be8c95746dd7b667cd 0.600000000000 1762866 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": 1275561, "vin": [ { "gen": { "height": 1275551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "796c2299578bea48aedb22ceab4a4067bc6aa4a622eb90be8c95746dd7b667cd" } } ], "extra": [ 1, 171, 80, 165, 94, 37, 231, 29, 150, 223, 213, 72, 177, 161, 239, 116, 29, 9, 61, 8, 217, 198, 181, 97, 38, 28, 188, 197, 103, 161, 159, 27, 40, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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