Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d57ad561f99dfe2e73706aaa8748f7e528384aa675be11f8a9f95aa97d55dda

Tx prefix hash: bfefa4a3bd21bd9626d05928143404f5ef4f2da7786440335e66e1ef4d657060
Tx public key: 5b3ae9717399e6a9c39aa3f890dcb6c0274499fe669968a67f23b2f2fa6010a7
Timestamp: 1759706617 Timestamp [UCT]: 2025-10-05 23:23:37 Age [y:d:h:m:s]: 00:088:14:38:47
Block: 1383614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63468 RingCT/type: yes/0
Extra: 015b3ae9717399e6a9c39aa3f890dcb6c0274499fe669968a67f23b2f2fa6010a7021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dd0357ea8d9d3bd5ae1741c63363f16518dae46cfb9ddf2ab427cb247c22143 0.600000000000 1871761 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": 1383624, "vin": [ { "gen": { "height": 1383614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dd0357ea8d9d3bd5ae1741c63363f16518dae46cfb9ddf2ab427cb247c22143" } } ], "extra": [ 1, 91, 58, 233, 113, 115, 153, 230, 169, 195, 154, 163, 248, 144, 220, 182, 192, 39, 68, 153, 254, 102, 153, 104, 166, 127, 35, 178, 242, 250, 96, 16, 167, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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