Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6ffa7a8a4f2a9320a4622eaa73b7b89bbc8f763397ecd448890f4b6b5fd2cf6

Tx prefix hash: 8c8b85505c954e515e0098807667645043620470afdca9e32037ab76aeffa64c
Tx public key: 70da60fe28094fdc95e6f7240f0a19e41a81f6472436b713cd17026fe984b16d
Timestamp: 1703595706 Timestamp [UCT]: 2023-12-26 13:01:46 Age [y:d:h:m:s]: 01:061:04:32:15
Block: 921556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304810 RingCT/type: yes/0
Extra: 0170da60fe28094fdc95e6f7240f0a19e41a81f6472436b713cd17026fe984b16d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9cc5b3a68538e60d7b2ab0b2aca176ae6e796bf8ee79e7de364c6a8f2a7b09e 0.600000000000 1379244 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": 921566, "vin": [ { "gen": { "height": 921556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9cc5b3a68538e60d7b2ab0b2aca176ae6e796bf8ee79e7de364c6a8f2a7b09e" } } ], "extra": [ 1, 112, 218, 96, 254, 40, 9, 79, 220, 149, 230, 247, 36, 15, 10, 25, 228, 26, 129, 246, 71, 36, 54, 183, 19, 205, 23, 2, 111, 233, 132, 177, 109, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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