Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cae7d8e509d9c4fa5ed75b28e43e3af6422fee8a85a8b8645eff719a2ef8e015

Tx prefix hash: 8fb03cf50ee95d4fa4e278abf44ed14a41f4468516a5b6c72ab28fa90b3a944c
Tx public key: 40d5c09ce8d3b883ae8eda91d416f86273266902ba60866260f3b5036547b802
Timestamp: 1724521981 Timestamp [UCT]: 2024-08-24 17:53:01 Age [y:d:h:m:s]: 00:232:23:15:55
Block: 1095062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166356 RingCT/type: yes/0
Extra: 0140d5c09ce8d3b883ae8eda91d416f86273266902ba60866260f3b5036547b80202110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5d6b4d98065d2e4ab7e00d0e88f4f6eb04ac40771e35e7f70687078774e392 0.600000000000 1570199 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": 1095072, "vin": [ { "gen": { "height": 1095062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5d6b4d98065d2e4ab7e00d0e88f4f6eb04ac40771e35e7f70687078774e392" } } ], "extra": [ 1, 64, 213, 192, 156, 232, 211, 184, 131, 174, 142, 218, 145, 212, 22, 248, 98, 115, 38, 105, 2, 186, 96, 134, 98, 96, 243, 181, 3, 101, 71, 184, 2, 2, 17, 0, 0, 0, 13, 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