Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971915cf935e8bfbdd82cbf679a2d5f410b7b14f8e0a1a1fee1051a2f1e9c5fa

Tx prefix hash: 1fb150256209423d416deed3b756e413f1a69d7663483efd39a692e3cbd258a3
Tx public key: ccb2b53b076cfd2bdcbc28263d30686d748549caddbdc9d5d2c0d50be0372737
Timestamp: 1698482853 Timestamp [UCT]: 2023-10-28 08:47:33 Age [y:d:h:m:s]: 01:159:14:02:18
Block: 879398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375030 RingCT/type: yes/0
Extra: 01ccb2b53b076cfd2bdcbc28263d30686d748549caddbdc9d5d2c0d50be03727370211000000084b8f5122000000000000000000

1 output(s) for total of 0.748535828000 dcy

stealth address amount amount idx
00: 1c6f3234c13d16c3da84543ab12a133bc4474f461fe765c0b6a65eaf6a4ea6ea 0.748535828000 1334912 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": 879408, "vin": [ { "gen": { "height": 879398 } } ], "vout": [ { "amount": 748535828, "target": { "key": "1c6f3234c13d16c3da84543ab12a133bc4474f461fe765c0b6a65eaf6a4ea6ea" } } ], "extra": [ 1, 204, 178, 181, 59, 7, 108, 253, 43, 220, 188, 40, 38, 61, 48, 104, 109, 116, 133, 73, 202, 221, 189, 201, 213, 210, 192, 213, 11, 224, 55, 39, 55, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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