Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9e62e71e191e503421b62f18f85bb937633caa6b023086cbce4ac8e40f8bad1

Tx prefix hash: 314b586d3774281e03e7fecee63640402b17420d2c2b26d0db53e700f9bd25af
Tx public key: d21d96cc95d357bdb1bcdbde6deaa9cd74dc3e43b8454e95339c5938f6e01df0
Timestamp: 1724926233 Timestamp [UCT]: 2024-08-29 10:10:33 Age [y:d:h:m:s]: 01:062:19:06:29
Block: 1098394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303325 RingCT/type: yes/0
Extra: 01d21d96cc95d357bdb1bcdbde6deaa9cd74dc3e43b8454e95339c5938f6e01df0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 592bf0ba4fc787f02afe0e11b5d9932033d93403683cebd4a205c917b5d46fcc 0.600000000000 1574095 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": 1098404, "vin": [ { "gen": { "height": 1098394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "592bf0ba4fc787f02afe0e11b5d9932033d93403683cebd4a205c917b5d46fcc" } } ], "extra": [ 1, 210, 29, 150, 204, 149, 211, 87, 189, 177, 188, 219, 222, 109, 234, 169, 205, 116, 220, 62, 67, 184, 69, 78, 149, 51, 156, 89, 56, 246, 224, 29, 240, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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