Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9699bec9bf0f2c9c66526ff4889b5737824943d82a0f5af199048a0160ce18be

Tx prefix hash: 4d6456b7bf1208b67acd3b2a8ede7fb4ee218197e9cfc6332e05fc2e802c0f23
Tx public key: 4d64a6fbbc8b818af66bfbafa13cc3673f16f9ddce5518cc204387c2222d8402
Timestamp: 1711683411 Timestamp [UCT]: 2024-03-29 03:36:51 Age [y:d:h:m:s]: 01:247:08:49:51
Block: 988624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435487 RingCT/type: yes/0
Extra: 014d64a6fbbc8b818af66bfbafa13cc3673f16f9ddce5518cc204387c2222d840202110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7c4f429c16c5427d64d659dcf0d6befe5986a1dc272b2c109843499ad2fcd2 0.600000000000 1448905 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": 988634, "vin": [ { "gen": { "height": 988624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7c4f429c16c5427d64d659dcf0d6befe5986a1dc272b2c109843499ad2fcd2" } } ], "extra": [ 1, 77, 100, 166, 251, 188, 139, 129, 138, 246, 107, 251, 175, 161, 60, 195, 103, 63, 22, 249, 221, 206, 85, 24, 204, 32, 67, 135, 194, 34, 45, 132, 2, 2, 17, 0, 0, 0, 10, 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