Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b261672e163fad6c2273a2376fbfcd09d6504da11221e7bf4397b4b598b712c

Tx prefix hash: e8f2c2d114681b8e4e2ad92824cda6ef6d5cc0e88686b616e874505a60e54602
Tx public key: a20a72816b113c314630f286a544b1c92fe19a83b4044ca6a27cc5e46b2a6c75
Timestamp: 1577555251 Timestamp [UCT]: 2019-12-28 17:47:31 Age [y:d:h:m:s]: 05:308:09:19:16
Block: 33664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367994 RingCT/type: yes/0
Extra: 01a20a72816b113c314630f286a544b1c92fe19a83b4044ca6a27cc5e46b2a6c75021100000078c3a1a09f000000000000000000

1 output(s) for total of 474.742432076000 dcy

stealth address amount amount idx
00: a2a3f4e443cc853d7de98af723c8b3dbdb60983cbaeb188e48e56ba0519f18e0 474.742432076000 56457 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": 33674, "vin": [ { "gen": { "height": 33664 } } ], "vout": [ { "amount": 474742432076, "target": { "key": "a2a3f4e443cc853d7de98af723c8b3dbdb60983cbaeb188e48e56ba0519f18e0" } } ], "extra": [ 1, 162, 10, 114, 129, 107, 17, 60, 49, 70, 48, 242, 134, 165, 68, 177, 201, 47, 225, 154, 131, 180, 4, 76, 166, 162, 124, 197, 228, 107, 42, 108, 117, 2, 17, 0, 0, 0, 120, 195, 161, 160, 159, 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