Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2caf090ce3b227ad1025b7ac11150a72a5fce0f073e2e15fe213157945609656

Tx prefix hash: d067e4f4e7bc66a71a9d71e693ff1b294fe0f9dd854e6d812f58434f24864a95
Tx public key: c49e10317274bc65f350c1cf6cd3baa9fe818dba36c601959ea9d6c30313d0e3
Timestamp: 1721609648 Timestamp [UCT]: 2024-07-22 00:54:08 Age [y:d:h:m:s]: 00:247:04:41:19
Block: 1070889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176580 RingCT/type: yes/0
Extra: 01c49e10317274bc65f350c1cf6cd3baa9fe818dba36c601959ea9d6c30313d0e3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3b98e2a52eca346a3f1c25df7bac6b1581a76501771b9c432e7d11326abbdba 0.600000000000 1542908 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": 1070899, "vin": [ { "gen": { "height": 1070889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3b98e2a52eca346a3f1c25df7bac6b1581a76501771b9c432e7d11326abbdba" } } ], "extra": [ 1, 196, 158, 16, 49, 114, 116, 188, 101, 243, 80, 193, 207, 108, 211, 186, 169, 254, 129, 141, 186, 54, 198, 1, 149, 158, 169, 214, 195, 3, 19, 208, 227, 2, 17, 0, 0, 0, 2, 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