Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241d15e818dfd79401e93c05bb6b6ce30bf7fb6575eb9408cb162fe3e24fbf64

Tx prefix hash: 6c99083d25f9c794ef36708297a62a594208db901f37cfb5eabf427caf02f501
Tx public key: 806970d5a7e59a1f6a2e8b1fb6af340307531ecb80bddc227b1bb2632a13a342
Timestamp: 1753226968 Timestamp [UCT]: 2025-07-22 23:29:28 Age [y:d:h:m:s]: 00:115:13:27:28
Block: 1331278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81392 RingCT/type: yes/0
Extra: 01806970d5a7e59a1f6a2e8b1fb6af340307531ecb80bddc227b1bb2632a13a3420211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a9b905e1bebcc63a40d22b67dd37546e5152c697634f39cd49caeeefc126c9 0.600000000000 1819073 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": 1331288, "vin": [ { "gen": { "height": 1331278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a9b905e1bebcc63a40d22b67dd37546e5152c697634f39cd49caeeefc126c9" } } ], "extra": [ 1, 128, 105, 112, 213, 167, 229, 154, 31, 106, 46, 139, 31, 182, 175, 52, 3, 7, 83, 30, 203, 128, 189, 220, 34, 123, 27, 178, 99, 42, 19, 163, 66, 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