Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6755d49794f9412b880d6739c57544819532e6f5ad08bba1ad4b2b5a6d12e23

Tx prefix hash: bb06a67c77853bb76e50cd4ff13448aeac1c3ba9802d024fc0d4c152c407b1f6
Tx public key: 991e986531d10bcfaf7bedb4c576a761f8599d784b5b93c3697662c8fe4ea72b
Timestamp: 1657151180 Timestamp [UCT]: 2022-07-06 23:46:20 Age [y:d:h:m:s]: 02:297:03:55:04
Block: 538203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733554 RingCT/type: yes/0
Extra: 01991e986531d10bcfaf7bedb4c576a761f8599d784b5b93c3697662c8fe4ea72b0211000000014da16a3a000000000000000000

1 output(s) for total of 10.109046445000 dcy

stealth address amount amount idx
00: 998ac61e55c6325c33d770bd84ddcaeae0d35d18129661599795b3512845ad3e 10.109046445000 968176 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": 538213, "vin": [ { "gen": { "height": 538203 } } ], "vout": [ { "amount": 10109046445, "target": { "key": "998ac61e55c6325c33d770bd84ddcaeae0d35d18129661599795b3512845ad3e" } } ], "extra": [ 1, 153, 30, 152, 101, 49, 209, 11, 207, 175, 123, 237, 180, 197, 118, 167, 97, 248, 89, 157, 120, 75, 91, 147, 195, 105, 118, 98, 200, 254, 78, 167, 43, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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