Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3b80879b10096343918d69b35378c9f462eadbba1415cdefb55cb16f315550

Tx prefix hash: a7c61a4882c4b039286f6233f3d776f1c25395fba15f7350468c9171af6a7ae7
Tx public key: 12c521ceadf191c39a8020206b784d6e054c5b7b672fa8ce95e2f394aaddafd5
Timestamp: 1700772771 Timestamp [UCT]: 2023-11-23 20:52:51 Age [y:d:h:m:s]: 01:138:12:22:51
Block: 898146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360170 RingCT/type: yes/0
Extra: 0112c521ceadf191c39a8020206b784d6e054c5b7b672fa8ce95e2f394aaddafd50211000000014b8f5122000000000000000000

1 output(s) for total of 0.648738168000 dcy

stealth address amount amount idx
00: 5d916b45c46c176ba3bf5b4bac8b99d5c73a01230448b97e5e7643d27dd600db 0.648738168000 1354551 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": 898156, "vin": [ { "gen": { "height": 898146 } } ], "vout": [ { "amount": 648738168, "target": { "key": "5d916b45c46c176ba3bf5b4bac8b99d5c73a01230448b97e5e7643d27dd600db" } } ], "extra": [ 1, 18, 197, 33, 206, 173, 241, 145, 195, 154, 128, 32, 32, 107, 120, 77, 110, 5, 76, 91, 123, 103, 47, 168, 206, 149, 226, 243, 148, 170, 221, 175, 213, 2, 17, 0, 0, 0, 1, 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