Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b69da4fd3b9de0cdaa455e0256497b140bf304a644de72e27de3847300a809f2

Tx prefix hash: 4585f9fe7b36e156324c38f07f4cf590ef6dd926467f240f9c530874ea49ee21
Tx public key: 598c710cb1023f019f8d7e06585266cef01a24891603b0ef489e9d7d3f2fb5b8
Timestamp: 1685328096 Timestamp [UCT]: 2023-05-29 02:41:36 Age [y:d:h:m:s]: 01:349:07:01:35
Block: 770357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510863 RingCT/type: yes/0
Extra: 01598c710cb1023f019f8d7e06585266cef01a24891603b0ef489e9d7d3f2fb5b8021100000003faf35c9c000000000000000000

1 output(s) for total of 1.719838402000 dcy

stealth address amount amount idx
00: f1cd02c064e8c225ef15f2fa318fb6a8ae9593a39837e3e60eb9ea83d9b96a75 1.719838402000 1219662 of 0

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": 770367, "vin": [ { "gen": { "height": 770357 } } ], "vout": [ { "amount": 1719838402, "target": { "key": "f1cd02c064e8c225ef15f2fa318fb6a8ae9593a39837e3e60eb9ea83d9b96a75" } } ], "extra": [ 1, 89, 140, 113, 12, 177, 2, 63, 1, 159, 141, 126, 6, 88, 82, 102, 206, 240, 26, 36, 137, 22, 3, 176, 239, 72, 158, 157, 125, 63, 47, 181, 184, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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