Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c23aa1e98263e12c785583ac4d794f82b1983d4c95b12a661519eec8a21e118d

Tx prefix hash: 92c3bba657318f62430a4229996bec9ac95f99d07947b49b1ca58b30376d16e0
Tx public key: ef0c2fa1bd3153f5252a7be5a15e5cfa92ea6298b48d77f8de6ad6e58e48a33c
Timestamp: 1675337934 Timestamp [UCT]: 2023-02-02 11:38:54 Age [y:d:h:m:s]: 01:341:20:09:43
Block: 688163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505292 RingCT/type: yes/0
Extra: 01ef0c2fa1bd3153f5252a7be5a15e5cfa92ea6298b48d77f8de6ad6e58e48a33c0211000000015029cbac000000000000000000

1 output(s) for total of 3.219809976000 dcy

stealth address amount amount idx
00: 467ab8246e6d66deb85dc1cb312c78066828191c605e0719152e5999361df354 3.219809976000 1130767 of 0

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": 688173, "vin": [ { "gen": { "height": 688163 } } ], "vout": [ { "amount": 3219809976, "target": { "key": "467ab8246e6d66deb85dc1cb312c78066828191c605e0719152e5999361df354" } } ], "extra": [ 1, 239, 12, 47, 161, 189, 49, 83, 245, 37, 42, 123, 229, 161, 94, 92, 250, 146, 234, 98, 152, 180, 141, 119, 248, 222, 106, 214, 229, 142, 72, 163, 60, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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