Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33cb4116f4dfb8ff24b2c236623341576f04f72de84392d8e8b4bfb79c3126e4

Tx prefix hash: fb74fdcc9ab4d20439424cc2d7c4b634858f41a5d50d4a6015476ffe30936641
Tx public key: 500b968e4a1c558cce4d8b25199347b37a967fe4d82ad1df05f925f3bf3cda9f
Timestamp: 1735667213 Timestamp [UCT]: 2024-12-31 17:46:53 Age [y:d:h:m:s]: 00:303:14:59:57
Block: 1187308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214509 RingCT/type: yes/0
Extra: 01500b968e4a1c558cce4d8b25199347b37a967fe4d82ad1df05f925f3bf3cda9f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7037d0791ff4f91e89e2e08ecbac8e39e439241dbf3d6126b21f77156ff865af 0.600000000000 1673797 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": 1187318, "vin": [ { "gen": { "height": 1187308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7037d0791ff4f91e89e2e08ecbac8e39e439241dbf3d6126b21f77156ff865af" } } ], "extra": [ 1, 80, 11, 150, 142, 74, 28, 85, 140, 206, 77, 139, 37, 25, 147, 71, 179, 122, 150, 127, 228, 216, 42, 209, 223, 5, 249, 37, 243, 191, 60, 218, 159, 2, 17, 0, 0, 0, 1, 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