Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35202adbc959beb572918c8ff1c8fd7613a69725489cc48eccd9abe3ea542057

Tx prefix hash: aef47e3611aea45807ad387f4c9a1f25616c879e4bfe68df28525185d4dd5637
Tx public key: d1951e11af1f8f0ef1c51adfc535b162a59a8a50314c3b5df8b642aac6dab5dd
Timestamp: 1751845538 Timestamp [UCT]: 2025-07-06 23:45:38 Age [y:d:h:m:s]: 00:180:12:48:44
Block: 1320250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127501 RingCT/type: yes/0
Extra: 01d1951e11af1f8f0ef1c51adfc535b162a59a8a50314c3b5df8b642aac6dab5dd02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c34e90c9aae41af31816b07a8553738661f35646ce67e8d96841ca6bfcc170f6 0.600000000000 1807947 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": 1320260, "vin": [ { "gen": { "height": 1320250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c34e90c9aae41af31816b07a8553738661f35646ce67e8d96841ca6bfcc170f6" } } ], "extra": [ 1, 209, 149, 30, 17, 175, 31, 143, 14, 241, 197, 26, 223, 197, 53, 177, 98, 165, 154, 138, 80, 49, 76, 59, 93, 248, 182, 66, 170, 198, 218, 181, 221, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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