Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74a13ec76b3f306efd6d21f50437b6af8fb5bb7aebe377a3646bf7961bc4367

Tx prefix hash: c1fff232255c2a63415ea2f2055c0cead0fc215bfd08bf822c07faf87281567a
Tx public key: 4a39ee965d9786f27a7439a7bf706381607103e4d15fb9ba40631d53d65d1e0b
Timestamp: 1752222888 Timestamp [UCT]: 2025-07-11 08:34:48 Age [y:d:h:m:s]: 00:201:21:27:31
Block: 1323169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142821 RingCT/type: yes/0
Extra: 014a39ee965d9786f27a7439a7bf706381607103e4d15fb9ba40631d53d65d1e0b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cf5c7439e20f567f273e64a86ecbeb9cf9b903fe1b6d2e4f0c80491f02bbd70 0.600000000000 1810904 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": 1323179, "vin": [ { "gen": { "height": 1323169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cf5c7439e20f567f273e64a86ecbeb9cf9b903fe1b6d2e4f0c80491f02bbd70" } } ], "extra": [ 1, 74, 57, 238, 150, 93, 151, 134, 242, 122, 116, 57, 167, 191, 112, 99, 129, 96, 113, 3, 228, 209, 95, 185, 186, 64, 99, 29, 83, 214, 93, 30, 11, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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