Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2d9168881e8470d4888125312de9671e7519ff0d9e26adda152e69ab3d34ec

Tx prefix hash: 3f1028ea7bc8c8bd34398a141ea6bae1dc3b0c409b0a83486d98deafed732d86
Tx public key: 97ebcffea20a58ed1ec7226b58e319a09d1ee2e18c44b0a66caa3c57fcd2758f
Timestamp: 1738898929 Timestamp [UCT]: 2025-02-07 03:28:49 Age [y:d:h:m:s]: 00:287:13:26:26
Block: 1213815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203264 RingCT/type: yes/0
Extra: 0197ebcffea20a58ed1ec7226b58e319a09d1ee2e18c44b0a66caa3c57fcd2758f02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f9208f472f56792bd6d5cc328d4ddb40bf800e4c3de6f7a822971eda2af6232 0.600000000000 1700596 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": 1213825, "vin": [ { "gen": { "height": 1213815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f9208f472f56792bd6d5cc328d4ddb40bf800e4c3de6f7a822971eda2af6232" } } ], "extra": [ 1, 151, 235, 207, 254, 162, 10, 88, 237, 30, 199, 34, 107, 88, 227, 25, 160, 157, 30, 226, 225, 140, 68, 176, 166, 108, 170, 60, 87, 252, 210, 117, 143, 2, 17, 0, 0, 0, 11, 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