Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 418f53504c2e746b3154dc7f321a96196319978b80997a033f08bf6cf3eafe59

Tx prefix hash: fa021a55dc6ae63ee904c13f0fd44f61fd468d4a0cad10946cb23ce07457ef8c
Tx public key: 41c40db8395334e21d7f1c4d3303bc6f89a36737a751cfa4fae641c0d82bb0ec
Timestamp: 1750412663 Timestamp [UCT]: 2025-06-20 09:44:23 Age [y:d:h:m:s]: 00:151:23:53:54
Block: 1308960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106472 RingCT/type: yes/0
Extra: 0141c40db8395334e21d7f1c4d3303bc6f89a36737a751cfa4fae641c0d82bb0ec021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c27358e6011f8d6fe330e1210aed753a05b3147620e93130a3bf4261b282c5d 0.600000000000 1796575 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": 1308970, "vin": [ { "gen": { "height": 1308960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c27358e6011f8d6fe330e1210aed753a05b3147620e93130a3bf4261b282c5d" } } ], "extra": [ 1, 65, 196, 13, 184, 57, 83, 52, 226, 29, 127, 28, 77, 51, 3, 188, 111, 137, 163, 103, 55, 167, 81, 207, 164, 250, 230, 65, 192, 216, 43, 176, 236, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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