Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f19c6c068d980607b9f615e8af5207d66625a4b57118444f7e036906a7af261e

Tx prefix hash: dc853b52dd43f5911c32e3b4f16a14c3ea94945cebdd6f851d3d96936e6551d5
Tx public key: 7215cf351546e2efdf558656d1edf738fe3148b822e491a061cdaf4fb4073e90
Timestamp: 1714363458 Timestamp [UCT]: 2024-04-29 04:04:18 Age [y:d:h:m:s]: 00:300:06:39:04
Block: 1010818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214628 RingCT/type: yes/0
Extra: 017215cf351546e2efdf558656d1edf738fe3148b822e491a061cdaf4fb4073e900211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e7801d39518a7bdc362a2fdfce85057ff0c902fdf285d682d2f3a5e282352f8 0.600000000000 1472876 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": 1010828, "vin": [ { "gen": { "height": 1010818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e7801d39518a7bdc362a2fdfce85057ff0c902fdf285d682d2f3a5e282352f8" } } ], "extra": [ 1, 114, 21, 207, 53, 21, 70, 226, 239, 223, 85, 134, 86, 209, 237, 247, 56, 254, 49, 72, 184, 34, 228, 145, 160, 97, 205, 175, 79, 180, 7, 62, 144, 2, 17, 0, 0, 0, 4, 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