Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e788746817603d1b41da2d5ebdd8c357ea82aeada80fddc32034d1f9f43f2468

Tx prefix hash: 9f66b301f0ef195282d6d5583d827e6593706b387e5ebc5ba5e286e033e3f2e7
Tx public key: f0ce69d694688cb3aa26c5fabae64964daf5bfc98eb1320cc872c3337c8598eb
Timestamp: 1760000055 Timestamp [UCT]: 2025-10-09 08:54:15 Age [y:d:h:m:s]: 00:093:11:29:13
Block: 1386047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66958 RingCT/type: yes/0
Extra: 01f0ce69d694688cb3aa26c5fabae64964daf5bfc98eb1320cc872c3337c8598eb02110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7108e69b14d521bed0f92a14b9da1b17ce36c05954ecfe273419ce3b8be9e5b1 0.600000000000 1874210 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": 1386057, "vin": [ { "gen": { "height": 1386047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7108e69b14d521bed0f92a14b9da1b17ce36c05954ecfe273419ce3b8be9e5b1" } } ], "extra": [ 1, 240, 206, 105, 214, 148, 104, 140, 179, 170, 38, 197, 250, 186, 230, 73, 100, 218, 245, 191, 201, 142, 177, 50, 12, 200, 114, 195, 51, 124, 133, 152, 235, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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