Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7e5579972da2c00a3b936eac7f8b075e6bfb88e6f37ea357f477088c12557b

Tx prefix hash: 45a54e530fcde0f62603800043552608b19b1c0b51a646ddf76f6f7f021a7167
Tx public key: a367b409ea048d608f2e5af01fd7e54cd67ad17adf28d3e8d09badd63b5d7df8
Timestamp: 1746344612 Timestamp [UCT]: 2025-05-04 07:43:32 Age [y:d:h:m:s]: 00:197:23:53:25
Block: 1275443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139216 RingCT/type: yes/0
Extra: 01a367b409ea048d608f2e5af01fd7e54cd67ad17adf28d3e8d09badd63b5d7df80211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7985ba98a9defa6f6719c81dae460a8977d9acad67a7b5a2bac9c095b2791fcc 0.600000000000 1762754 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": 1275453, "vin": [ { "gen": { "height": 1275443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7985ba98a9defa6f6719c81dae460a8977d9acad67a7b5a2bac9c095b2791fcc" } } ], "extra": [ 1, 163, 103, 180, 9, 234, 4, 141, 96, 143, 46, 90, 240, 31, 215, 229, 76, 214, 122, 209, 122, 223, 40, 211, 232, 208, 155, 173, 214, 59, 93, 125, 248, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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