Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5e84c792e41e9a59da64ca797ef6e682e2db29583e93077cf8890bc7030d08

Tx prefix hash: 0331d115e76b2db4627de2b02ac64a604c8102997b678764c58a90b043b4a923
Tx public key: ab578b5be113b1d38ac16adf28894aeb5ef5b8d4c3f3ba33bc36f58e42fd556a
Timestamp: 1709088049 Timestamp [UCT]: 2024-02-28 02:40:49 Age [y:d:h:m:s]: 01:252:00:24:29
Block: 967098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438822 RingCT/type: yes/0
Extra: 01ab578b5be113b1d38ac16adf28894aeb5ef5b8d4c3f3ba33bc36f58e42fd556a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5bbc9231704db19c5a8e8a59a9bd7a6ee0725da52a0ac47de7c40de477d05a0 0.600000000000 1426869 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": 967108, "vin": [ { "gen": { "height": 967098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5bbc9231704db19c5a8e8a59a9bd7a6ee0725da52a0ac47de7c40de477d05a0" } } ], "extra": [ 1, 171, 87, 139, 91, 225, 19, 177, 211, 138, 193, 106, 223, 40, 137, 74, 235, 94, 245, 184, 212, 195, 243, 186, 51, 188, 54, 245, 142, 66, 253, 85, 106, 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