Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4f0e276a2c982587a0eca5e9793fdc4bbbe42a39bee69a86e9797a80be9938

Tx prefix hash: 5a07117012ee5fa31ebf67db44ce3aa74a2595e52bda089bab3eadd9ea5defc3
Tx public key: 04ebcf0d7727d63e05ea83d0da3543db39dff4251c68fb999e65e934ecf792e9
Timestamp: 1732484761 Timestamp [UCT]: 2024-11-24 21:46:01 Age [y:d:h:m:s]: 00:205:20:50:42
Block: 1160958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146869 RingCT/type: yes/0
Extra: 0104ebcf0d7727d63e05ea83d0da3543db39dff4251c68fb999e65e934ecf792e90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4847afcde09cafa860aad96a68c6e808857d410af2b35fb026d4281ba87c2db1 0.600000000000 1646609 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": 1160968, "vin": [ { "gen": { "height": 1160958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4847afcde09cafa860aad96a68c6e808857d410af2b35fb026d4281ba87c2db1" } } ], "extra": [ 1, 4, 235, 207, 13, 119, 39, 214, 62, 5, 234, 131, 208, 218, 53, 67, 219, 57, 223, 244, 37, 28, 104, 251, 153, 158, 101, 233, 52, 236, 247, 146, 233, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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