Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edbecc0e01a1ae0122abd39e7a960ab65f5c5a6038cda0c7d74c3180fd49de73

Tx prefix hash: 8a504f8b4810ccc306d3473d3c6413f6ed717f90d59eea62cb3fd52dc328a286
Tx public key: 7053e2d6403f4cb789bdf78579f7118c73e83228b578524aee013f6d5b9008cc
Timestamp: 1681214113 Timestamp [UCT]: 2023-04-11 11:55:13 Age [y:d:h:m:s]: 01:291:11:07:30
Block: 736240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469671 RingCT/type: yes/0
Extra: 017053e2d6403f4cb789bdf78579f7118c73e83228b578524aee013f6d5b9008cc021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.231163905000 dcy

stealth address amount amount idx
00: e83f4b8835253936495c393fdf4fb575cd21cdf1912ee2d7b0dcd2821c2fb668 2.231163905000 1182657 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": 736250, "vin": [ { "gen": { "height": 736240 } } ], "vout": [ { "amount": 2231163905, "target": { "key": "e83f4b8835253936495c393fdf4fb575cd21cdf1912ee2d7b0dcd2821c2fb668" } } ], "extra": [ 1, 112, 83, 226, 214, 64, 63, 76, 183, 137, 189, 247, 133, 121, 247, 17, 140, 115, 232, 50, 40, 181, 120, 82, 74, 238, 1, 63, 109, 91, 144, 8, 204, 2, 17, 0, 0, 0, 2, 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