Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99cea8088872f79b85e2750cf4f8057776f1eef64048b1cf5a3451b582f4c91b

Tx prefix hash: 34de3480dcc5200d3adb3810267a507d4cb623bfb4f8688bbdaf8c7338e121b2
Tx public key: 9f28bb8aec36850bac2cd2f08fd7a40ab49f24f326b5dee84c3b8627d6b81364
Timestamp: 1709536735 Timestamp [UCT]: 2024-03-04 07:18:55 Age [y:d:h:m:s]: 00:330:19:22:49
Block: 970815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236534 RingCT/type: yes/0
Extra: 019f28bb8aec36850bac2cd2f08fd7a40ab49f24f326b5dee84c3b8627d6b8136402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80716679e4beb8b291f6189735afb914e5c723c57d79362f31b438d18aab9862 0.600000000000 1430678 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": 970825, "vin": [ { "gen": { "height": 970815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80716679e4beb8b291f6189735afb914e5c723c57d79362f31b438d18aab9862" } } ], "extra": [ 1, 159, 40, 187, 138, 236, 54, 133, 11, 172, 44, 210, 240, 143, 215, 164, 10, 180, 159, 36, 243, 38, 181, 222, 232, 76, 59, 134, 39, 214, 184, 19, 100, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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