Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca6e64ae94905a6416e85fb6ae480c78c06f32c5ec8326f5332fcc1d343b556e

Tx prefix hash: 29273b32c7d2dcae5bf981493e408510563eac7c3bdf35ca8532c18ee511e780
Tx public key: 626dd5a1bb3e19fc1d28575425df85476a311747e69fef7479be565120714e47
Timestamp: 1695478167 Timestamp [UCT]: 2023-09-23 14:09:27 Age [y:d:h:m:s]: 02:044:15:13:06
Block: 854456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551534 RingCT/type: yes/0
Extra: 01626dd5a1bb3e19fc1d28575425df85476a311747e69fef7479be565120714e47021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.905383594000 dcy

stealth address amount amount idx
00: 3bd89247e6e43a3506a1958cb76ebf71e29e26e358433a8b85b9ce6e1c4d82a1 0.905383594000 1308430 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": 854466, "vin": [ { "gen": { "height": 854456 } } ], "vout": [ { "amount": 905383594, "target": { "key": "3bd89247e6e43a3506a1958cb76ebf71e29e26e358433a8b85b9ce6e1c4d82a1" } } ], "extra": [ 1, 98, 109, 213, 161, 187, 62, 25, 252, 29, 40, 87, 84, 37, 223, 133, 71, 106, 49, 23, 71, 230, 159, 239, 116, 121, 190, 86, 81, 32, 113, 78, 71, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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