Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab7f61a6cf8d5665bdc762827bdbc93b734371d8997b2694bda6037da6c92f05

Tx prefix hash: b3a7e421cc2bab40754a497cabb6908f0d58ed4a17841ff28bc04d0853058f8d
Tx public key: 34422f829b80e5a354c578b2beb5d6c115a8a5bb0228cbdf657bef60b9b9d87b
Timestamp: 1763807883 Timestamp [UCT]: 2025-11-22 10:38:03 Age [y:d:h:m:s]: 00:007:13:55:28
Block: 1417604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5449 RingCT/type: yes/0
Extra: 0134422f829b80e5a354c578b2beb5d6c115a8a5bb0228cbdf657bef60b9b9d87b02110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57ae900af4037f9aa8e6595bae4e3dad6799270ebd7476884c9c77e6c4a77e92 0.600000000000 1906129 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": 1417614, "vin": [ { "gen": { "height": 1417604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57ae900af4037f9aa8e6595bae4e3dad6799270ebd7476884c9c77e6c4a77e92" } } ], "extra": [ 1, 52, 66, 47, 130, 155, 128, 229, 163, 84, 197, 120, 178, 190, 181, 214, 193, 21, 168, 165, 187, 2, 40, 203, 223, 101, 123, 239, 96, 185, 185, 216, 123, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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