Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985c334a89cb8f615d758a8891fb73e163073926ba93cf8fca55ab194b8e8244

Tx prefix hash: 1068f4957b81e7799a98a6bb48a2ed09d351244897bae0d00c2d5d0295c32e77
Tx public key: e927c92c89df3ab4dcc965de516b6c9e630350b80d71f4e0df1140b2a0b774d0
Timestamp: 1704044409 Timestamp [UCT]: 2023-12-31 17:40:09 Age [y:d:h:m:s]: 01:137:09:16:23
Block: 925275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359328 RingCT/type: yes/0
Extra: 01e927c92c89df3ab4dcc965de516b6c9e630350b80d71f4e0df1140b2a0b774d00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9476b2f54851b21ff8e4f7529974d89f5582474d0f596186868d77e291e073a9 0.600000000000 1383035 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": 925285, "vin": [ { "gen": { "height": 925275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9476b2f54851b21ff8e4f7529974d89f5582474d0f596186868d77e291e073a9" } } ], "extra": [ 1, 233, 39, 201, 44, 137, 223, 58, 180, 220, 201, 101, 222, 81, 107, 108, 158, 99, 3, 80, 184, 13, 113, 244, 224, 223, 17, 64, 178, 160, 183, 116, 208, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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