Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7d676c1891f6f785fe550839956712b6bd92dfccb80bc450d5e7688915347a

Tx prefix hash: ebb9f6daf09844c4b106666a87d5553b05a0eb2e0f9edfbfcadaad2991d05d3b
Tx public key: 2608b88c6647156251b202e889e6e3f35fe8331ef5084f327f6173a1cb7ec895
Timestamp: 1695793987 Timestamp [UCT]: 2023-09-27 05:53:07 Age [y:d:h:m:s]: 01:235:15:55:49
Block: 857075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429514 RingCT/type: yes/0
Extra: 012608b88c6647156251b202e889e6e3f35fe8331ef5084f327f6173a1cb7ec89502110000000b33af99f4000000000000000000

1 output(s) for total of 0.887472251000 dcy

stealth address amount amount idx
00: f5fb7ad2994987341fbcc20a1e1ab787a8a5e96daf09c99c8cb9690d438def4a 0.887472251000 1311179 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": 857085, "vin": [ { "gen": { "height": 857075 } } ], "vout": [ { "amount": 887472251, "target": { "key": "f5fb7ad2994987341fbcc20a1e1ab787a8a5e96daf09c99c8cb9690d438def4a" } } ], "extra": [ 1, 38, 8, 184, 140, 102, 71, 21, 98, 81, 178, 2, 232, 137, 230, 227, 243, 95, 232, 51, 30, 245, 8, 79, 50, 127, 97, 115, 161, 203, 126, 200, 149, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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