Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56b64e4589b71943cdd6869ace17b62eabecab5ea2fa78d2e6fe0a819f445e1

Tx prefix hash: fd4c7e96eff8c5f2afcfaaa8ca2494da680b32990069c387c435a4f790bf3038
Tx public key: bc830111955ef690287dc5a6a5ccb4f0d20b8f87e12e0ede156acc3c3e080395
Timestamp: 1745689696 Timestamp [UCT]: 2025-04-26 17:48:16 Age [y:d:h:m:s]: 00:213:20:31:20
Block: 1270027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150562 RingCT/type: yes/0
Extra: 01bc830111955ef690287dc5a6a5ccb4f0d20b8f87e12e0ede156acc3c3e0803950211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5a407c3edf036234d1dd8c89666bf43a13b77520929ddb49f602b9bf14b7bd5 0.600000000000 1757268 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": 1270037, "vin": [ { "gen": { "height": 1270027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5a407c3edf036234d1dd8c89666bf43a13b77520929ddb49f602b9bf14b7bd5" } } ], "extra": [ 1, 188, 131, 1, 17, 149, 94, 246, 144, 40, 125, 197, 166, 165, 204, 180, 240, 210, 11, 143, 135, 225, 46, 14, 222, 21, 106, 204, 60, 62, 8, 3, 149, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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