Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 523e7ed1445364648921a6d98747b9ae5f5a15f4a7ffcf7f9c8df07ad325c26a

Tx prefix hash: 33561cc42a78325b3705432f4793b8f4589fc63b2cbd803167b084b1f2466db3
Tx public key: 336fba82356a32353bcbd29f14d3466f5f98d34dd734a5264f55301996a3d4bf
Timestamp: 1741020198 Timestamp [UCT]: 2025-03-03 16:43:18 Age [y:d:h:m:s]: 00:262:23:12:20
Block: 1231362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185681 RingCT/type: yes/0
Extra: 01336fba82356a32353bcbd29f14d3466f5f98d34dd734a5264f55301996a3d4bf021100000012007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9647c3df5e983f8aa0574b7436c4e8df2c85c63cdc2d937832bb4c72c3e4d273 0.600000000000 1718269 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": 1231372, "vin": [ { "gen": { "height": 1231362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9647c3df5e983f8aa0574b7436c4e8df2c85c63cdc2d937832bb4c72c3e4d273" } } ], "extra": [ 1, 51, 111, 186, 130, 53, 106, 50, 53, 59, 203, 210, 159, 20, 211, 70, 111, 95, 152, 211, 77, 215, 52, 165, 38, 79, 85, 48, 25, 150, 163, 212, 191, 2, 17, 0, 0, 0, 18, 0, 127, 151, 138, 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