Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bf7a8929e336cf5db6c92d10e2ffc17c17f222a91413a5f6591c9572cfbef74

Tx prefix hash: 5f2b00dfc7207b1d17a2519d93ec062551ace38ade922c243ac5d63027047f9d
Tx public key: 4fa2571e7134c11f4caaaa7ffe44011ea4c70c3b2d5ae0c055a34ea381434d91
Timestamp: 1638785777 Timestamp [UCT]: 2021-12-06 10:16:17 Age [y:d:h:m:s]: 03:330:02:13:08
Block: 389579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1012349 RingCT/type: yes/0
Extra: 014fa2571e7134c11f4caaaa7ffe44011ea4c70c3b2d5ae0c055a34ea381434d91021100000001cc317103000000000000000000

1 output(s) for total of 31.416906372000 dcy

stealth address amount amount idx
00: bd68520fac189a5a448cf379f3459d97624217f893f6b1a88b458e797d61fcfb 31.416906372000 784804 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": 389589, "vin": [ { "gen": { "height": 389579 } } ], "vout": [ { "amount": 31416906372, "target": { "key": "bd68520fac189a5a448cf379f3459d97624217f893f6b1a88b458e797d61fcfb" } } ], "extra": [ 1, 79, 162, 87, 30, 113, 52, 193, 31, 76, 170, 170, 127, 254, 68, 1, 30, 164, 199, 12, 59, 45, 90, 224, 192, 85, 163, 78, 163, 129, 67, 77, 145, 2, 17, 0, 0, 0, 1, 204, 49, 113, 3, 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