Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bef408ce463ccaa3e2138bda4064931017e342ae7af9ed7bcd2320b2b7d7c85

Tx prefix hash: 469e4a29fa1660cdf1b4feb6bfa129bbcaf3018bc01ee3289d3df4a045166e30
Tx public key: e12a1da41381c0fe5d66c61482fe33ac143002b3fd9bc3e0303718b6f8324ef5
Timestamp: 1677132279 Timestamp [UCT]: 2023-02-23 06:04:39 Age [y:d:h:m:s]: 02:002:08:58:16
Block: 703041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523250 RingCT/type: yes/0
Extra: 01e12a1da41381c0fe5d66c61482fe33ac143002b3fd9bc3e0303718b6f8324ef5021100000003e6d27f9c000000000000000000

1 output(s) for total of 2.874307510000 dcy

stealth address amount amount idx
00: 1ef87220f48ff05a3c7042ef7129e36ad833379d06232a993eecd81f540bc7e0 2.874307510000 1146596 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": 703051, "vin": [ { "gen": { "height": 703041 } } ], "vout": [ { "amount": 2874307510, "target": { "key": "1ef87220f48ff05a3c7042ef7129e36ad833379d06232a993eecd81f540bc7e0" } } ], "extra": [ 1, 225, 42, 29, 164, 19, 129, 192, 254, 93, 102, 198, 20, 130, 254, 51, 172, 20, 48, 2, 179, 253, 155, 195, 224, 48, 55, 24, 182, 248, 50, 78, 245, 2, 17, 0, 0, 0, 3, 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