Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79e4762ac6d5a8e69a04e23bfeb10156714b0483f59c08645df82bc7f3c1f524

Tx prefix hash: 8e47853367eb41ec243925ab6a0ce4e96741e173ca969e6b853c6a841ec9605c
Tx public key: 75e906cedb36b346eb2b9bad9ecb9302c03b959840d63ad2cf164e6880aa1da0
Timestamp: 1698309807 Timestamp [UCT]: 2023-10-26 08:43:27 Age [y:d:h:m:s]: 01:199:22:03:39
Block: 877948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403900 RingCT/type: yes/0
Extra: 0175e906cedb36b346eb2b9bad9ecb9302c03b959840d63ad2cf164e6880aa1da00211000000024b8f5122000000000000000000

1 output(s) for total of 0.756822157000 dcy

stealth address amount amount idx
00: a505fa9eeb5cedf271339a5312351fbd0a8080badadc82ba5bc2f9f0f2ceea70 0.756822157000 1333350 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": 877958, "vin": [ { "gen": { "height": 877948 } } ], "vout": [ { "amount": 756822157, "target": { "key": "a505fa9eeb5cedf271339a5312351fbd0a8080badadc82ba5bc2f9f0f2ceea70" } } ], "extra": [ 1, 117, 233, 6, 206, 219, 54, 179, 70, 235, 43, 155, 173, 158, 203, 147, 2, 192, 59, 149, 152, 64, 214, 58, 210, 207, 22, 78, 104, 128, 170, 29, 160, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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